This section describes the service-level and component-level security for each CygNet service.
Information provided for each service includes:
| Service Application Name | Main Security Event | Component-Level Security | Subject to Application Override |
|---|---|---|---|
|
The service’s security Application name. If this name is defined in the service configuration file it can be changed. The service must be stopped and restarted for the change to become effective and security must be defined under the new name. |
The service’s main security event. If this name is defined in the service configuration file it can be changed. The service must be stopped and restarted for the change to become effective and security must be defined under the new name. Note: The main security event is the event for which Admin override privileges apply. This means that if a service has more than one event, and if the user has Level 5 (Admin) permission for the main security event, then the user has full permission for all service Events (except ODBC) regardless of the authorization for those Events. |
Yes indicates that security can be applied to components within the service (for example, individual records). For component-level security, the Application and, in some cases, the Event names generally are user-defined. |
Yes indicates point records in the service are subject to security defined in the FAC or PNT. |
More:
Address Resolution Service (ARS)
BLOB Storage Service (BSS and APPS)
Device Definition Service (DDS)
Event Logging Service (ELS and ELSALM)
Flow Measurement Service (FMS)
General Notification Service (GNS)
HyperPoint Scripting Service (HSS)
Master Scheduling Service (MSS)
Service Monitor Service (SVCMON)
Universal Interface Service (UIS)